Skip to content

docs: document deleting custom identity schemas (do not merge)#2539

Open
KT-Doan wants to merge 3 commits intoory:masterfrom
KT-Doan:feat/document-identity-schema-delete
Open

docs: document deleting custom identity schemas (do not merge)#2539
KT-Doan wants to merge 3 commits intoory:masterfrom
KT-Doan:feat/document-identity-schema-delete

Conversation

@KT-Doan
Copy link
Copy Markdown
Contributor

@KT-Doan KT-Doan commented May 4, 2026

Summary

Adds a "Delete a custom schema" section to the manage identity schemas page, covering both the Console UI flow and a cURL example using a workspace API key against the Console API.

Documents the constraints surfaced by the API: the deletion is rejected (409) if the schema is still attached to a project or referenced by an identity. The section also calls out that presets cannot be deleted and that an attachment to a project is permanent for the lifetime of that project.

Pairs with the cloud-side endpoint and Console UI changes that introduced the delete capability.

Test plan

  • Local docusaurus build renders the new section without lint errors
  • Links to personal-access-token.mdx#authorizing-ory-network-workspace-admin-apis resolve
  • <ConsoleLink route="project.identitySchema" /> resolves to the existing schema page

@KT-Doan KT-Doan changed the title docs: document deleting custom identity schemas docs: document deleting custom identity schemas (do not merge) May 4, 2026
Comment thread docs/identities/model/manage-identity-schema.mdx Outdated
Comment thread docs/identities/model/manage-identity-schema.mdx Outdated
Comment thread docs/identities/model/manage-identity-schema.mdx Outdated
Co-authored-by: unatasha8 <una.cogavin@ory.sh>
@unatasha8
Copy link
Copy Markdown
Contributor

What do you mean by "an attachment to a project is permanent for the lifetime of that project"? You are able to change a project's schema so a schema is not permanently 'attached' for the lifetime of the project.

@KT-Doan
Copy link
Copy Markdown
Contributor Author

KT-Doan commented May 7, 2026

What do you mean by "an attachment to a project is permanent for the lifetime of that project"? You are able to change a project's schema so a schema is not permanently 'attached' for the lifetime of the project.

When we add a schema to a project its attached to the historical project revision, so identities can still reference that schema even if it's technically not in the project's current state

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants